Skip Headers

Oracle® Enterprise Manager Advanced Configuration 10g Release 2 (10.2) Part Number B16242-02 |
Home | Book List | Contents | Index | Master Index | Feedback

Previous | Next
| View PDF

# 7 Locating and Configuring Enterprise Manager Log Files

When you install the Oracle Management Agent or the Oracle Management Service, Enterprise Manager automatically configures the system to save certain informational, warning, and error information to a set of log files.

Log files can help you troubleshoot potential problems with an Enterprise Manager installation. They provide detailed information about the actions performed by Enterprise Manager and whether or not any warnings or errors occurred.

This chapter not only helps you locate and review the contents of Enterprise Manager log files, but also includes instructions for configuring the log files to provide more detailed information to help in troubleshooting or to provide less detailed information to save disk space.

This chapter contains the following sections:

- Locating and Configuring Management Agent Log and Trace Files

- Locating and Configuring Management Service Log and Trace Files

## 7.1 Locating and Configuring Management Agent Log and Trace Files

The following sections provide information on the log and trace files for the Oracle Management Agent:

- About the Management Agent Log and Trace Files

- Locating the Management Agent Log and Trace Files

- About Management Agent Rollover Files

- Controlling the Size and Number of Management Agent Log and Trace Files

- Controlling the Size and Number of Fetchlet Log and Trace Files

- Controlling the Contents of the Fetchlet Trace File

### 7.1.1 About the Management Agent Log and Trace Files

Oracle Management Agent log and trace files store important information that support personnel can later use to troubleshoot problems. The Management Agent uses three types of log files:

- The Management Agent log file (`emagent.log`)

  The Agent saves information to the log file when the Agent performs an action (such as starting, stopping, or connecting to a Management Service) or when the Agent generates an error (for example, when the Agent cannot connect to the Management Service).

- The Management Agent trace file (`emagent.trc`)

  The Management Agent trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about what actions the Agent was performing when a particular problem occurred.

- The Management Agent startup log file (`emagent.nohup`)

  The Management Agent saves information to the startup log file when there is a problem starting the agent. This file is updated by the Management Agent Watchdog Process. When the Watchdog Process finds any problems, it logs to this file.

See Also: "About the Management Agent Watchdog Process"

In addition, Enterprise Manager also provides a log file and a trace file for the fetchlets, which are software programs used by the Management Agent for certain data-gathering tasks:

- `emagentfetchlet.log`

- `emagentfetchlet.trc`

### 7.1.2 Locating the Management Agent Log and Trace Files

The Management Agent log files are stored in the following directory when you install the Management Agent:

    AGENT_HOME/sysman/log/

See Also: Chapter 1, "Introduction to Enterprise Manager Advanced Configuration" for information about locating the Agent home directory.

### 7.1.3 About Management Agent Rollover Files

Both the Management Agent log file and the Management Agent trace file are designed to increase in size over time as information is written to the files. However, they are also designed to reach a maximum size. When the files reach the predefined maximum size, the Management Agent renames (or rolls) the logging or trace information to a new file name and starts a new log or trace file. This process keeps the log files from growing too large.

To be sure you have access to important log or trace file information, the Management Agent will rollover the log and trace files four times by default. When it rolls the log or trace file over the fourth time, the Agent deletes the oldest rollover file.

As a result, you will often see a total of four log files and four trace files in the log directory. The following example shows three archived trace files and the current trace file in the `AGENT_HOME/sysman/log` directory:

    emagent.trc
    emagent.trc.1
    emagent.trc.2
    emagent.trc.3

### 7.1.4 Controlling the Size and Number of Management Agent Log and Trace Files

You can control how large the log file and the trace file can get before the Management Agent creates a rollover file. You can also control how many rollover files are created before the Management Agent deletes any logging or tracing data.

To control the size and number of Management Agent Log and Trace Files:

1. Stop the Management Agent.

   See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX"

2. Locate the `emd.properties` file, which is located in the following directory:

       AGENT_HOME/sysman/config/ (UNIX)
       AGENT_HOME\sysman\config (Windows)

3. Use a text editor to open the `emd.properties` file.

4. Use the information in Table 7-1 to locate and modify the Agent logging and tracing properties in the `emd.properties` file.

5. Restart the Management Agent.

Table 7-1 Management Agent Log and Trace File Properties

Property | Purpose | Example
--- | --- | ---
    LogFilewithPID
| When set to TRUE, this property appends the process ID of the Management Agent to the log file name. This makes it easier to identify the process ID of the Management Agent you are monitoring. | `LogFilewithPID=true`
    LogFileMaxSize
| When the Agent log file reaches this size (in kilobytes), the Management Agent `copies the logging data to a new rollover file and creates a new emagent.log` logging file. | `LogFileMaxSize=4096`
    LogFileMaxRolls
| By the default, the Agent will rollover the log file four times before it deletes any logging data. The number of rollover files is controlled by this property. | `LogFileMaxRolls=4`
    TrcFileMaxSize
| When the Agent trace file reach this size (in kilobytes), the Management Agent `copies the logging data to a new rollover file and creates a new emagent.trc` logging file. | TrcFileMaxSize=4096
TrcFileMaxRolls | By the default, the Agent will rollover the trace file four times before it deletes any tracing data. The number of rollover files is controlled by this property. | TrcFileMaxRolls=4

### 7.1.5 Controlling the Contents of the Management Agent Trace File

To modify the amount of information save d in the Management Agent trace file:

1. Stop the Management Agent.

   See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX"

2. Locate the `emd.properties` file, which is located in the following directory:

       AGENT_HOME/sysman/config

3. Open the `emd.properties` file using your favorite text editor and look for the following entries near the bottom of the file:

       tracelevel.main=WARN
       tracelevel.emdSDK=WARN
       tracelevel.emdSDK.util=WARN
       tracelevel.ResMonitor=WARN
       tracelevel.Dispatcher=WARN
       tracelevel.ThreadPool=WARN
       tracelevel.pingManger=WARN
       .
       .
       .

   Each of these properties controls the level of logging detail for the various subcomponents of the Management Agent.

4. Modify the amount of information that is included in the trace file by replacing the WARN value for each property to one of the values shown in Table 7-2.

   Note: The values described in Table 7-2 are case-sensitive.

5. Restart the Management Agent.

Table 7-2 Enterprise Manager Component Tracing Levels

Level | Purpose
--- | ---
ERROR | Include only critical errors in the trace file. This setting generates the least amount of tracing data. The trace file will likely grow at a relatively slow rate when you select this logging level.
WARN | Include warning information, in addition to critical errors.
INFO | Include informational messages, in addition to warning and critical error information.
DEBUG | Include debugging information, as well as informational tracing, warning, and critical errors. This setting generates the greatest amount of tracing data. Note: The trace file will likely grow at a relatively fast rate when you select this logging level.

### 7.1.6 Controlling the Size and Number of Fetchlet Log and Trace Files

Like the Management Agent log and trace files, the Management Agent fetchlet log and trace files are designed to reach a maximum size before the Management Agent renames (or rolls) the information to a new file name and starts a new log or trace file.

To control the maximum size of the Management Agent fetchlet log and trace files, as well as the number of rollover files:

1. Stop the Management Agent.

   See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX"

2. Locate the `emagentlogging.properties` file in the following directory:

       AGENT_HOME/sysman/config

3. Open the `emagentlogging.properties` file with a text editor and modify the entries described in Table 7-3.

4. Restart the Management Agent.

Table 7-3 Management Agent Servlet Log and Trace File Properties

Property | Purpose | Example
--- | --- | ---
log4j.appender. emagentlogAppender. MaxFileSize | When the fetchlet log file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new `emagentfetchlet.log` file. | log4j.appender. emagentlogAppender. MaxFileSize=20000000
log4j.appender. emagentlogAppender. MaxBackupIndex | This optional property indicates how many times the Management Agent will rollover the fetchlet log file to a new file name before deleting logging data. Note: Because the log file does not contain as much data as the trace file, it is usually not necessary to create more than one rollover file. As a result, this entry is not included in the properties file by default. | log4j.appender.emagentlogAppender. MaxBackupIndex=1
log4j.appender. emagenttrcAppender. MaxFileSize | When the fetchlet trace file reaches this size, the Management Agent copies the logging data to a new rollover file and creates a new `emagentfetchlet.trc` log file. | log4j.appender. emagenttrcAppender. MaxFileSize=5000000
log4j.appender. emagenttrcAppender. MaxBackupIndex | This property indicates how many times the Management Agent will rollover the trace file to a new file name before deleting tracing data. | log4j.appender. emagenttrcAppender. MaxBackupIndex=10

### 7.1.7 Controlling the Contents of the Fetchlet Trace File

By default, the Management Agent will save all critical and warning messages generated by the Management Agent fetchlets to the `emagentfetchlet.trc` file. However, you can adjust the amount of logging information that the fetchlets generate.

To change the amount of tracing information generated by the Management Agent fetchlets:

1. Stop the Management Agent.

   See Also: "Starting, Stopping, and Checking the Status of the Management Agent on UNIX"

2. Locate the `emagentlogging.properties` file in the following directory:

       AGENT_HOME/sysman/config

3. Open the `emagentlogging.properties` file with a text editor and locate the following entry:

       log4j.rootCategory=WARN, emagentlogAppender, emagenttrcAppender

4. Change the value of the `log4j.rootCategory` parameter to one of the values shown in Table 7-2.

   Note: The the values described in Table 7-2 are case-sensitive.

5. Restart the Management Agent.

## 7.2 Locating and Configuring Management Service Log and Trace Files

The following sections describe how to locate and configure the Management Service log files:

- Locating the Management Service Log and Trace Files

- Controlling the Size and Number of Management Service Log and Trace Files

- Controlling the Contents of the Management Service Trace File

- Controlling the Oracle Application Server Log Files

### 7.2.1 About the Management Service Log and Trace Files

Oracle Management Service log and trace files store important information that support personnel can later use to troubleshoot problems. The Management Service uses two types of log files:

- The Management Service log file (`emoms.log`)

  The Oracle Management Service saves information to the log file when the Management Service performs an action (such as starting or stopping) or when the Management Service generates an error.

- The Management Service trace file (`emoms.trc`)

  The Management Service trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about what actions the Management Service was performing when a particular problem occurred.

### 7.2.2 Locating the Management Ser vice Log and Trace Files

The Management Service log and trace files are stored in the following directory inside the Oracle Application Server Home where the Oracle Management Service is installed and deployed:

    AS_HOME/sysman/log/

### 7.2.3 Controlling the Size and Number of Management Service Log and Trace Files

The Management Service log and trace files increases in size over time as information is written to the files. However, the files are designed to reach a maximum size. When the files reach the predefined maximum size, the Management Service renames (or rolls) the logging information to a new file name and starts a new log or trace file. This process keeps the log and trace files from growing too large.

As a result, you will often see multiple log and trace files in the Management Service log directory. The following example shows one archived log file and the current log file in the `AS_HOME/sysman/log` directory:

    emoms.log
    emoms.log.1

To control the maximum size of the Management Service log and trace files, as well as the number of rollover files:

1. Stop the Management Service.

   See Also: "Controlling the Oracle Management Service"

2. Locate the `emomslogging.properties` file in the following directory:

       AS_HOME/sysman/config

3. Open the `emomslogging.properties` file with a text editor and modify the entries described in Table 7-4.

4. Restart the Management Service.

Table 7-4 Management Service Log File Properties in the emomslogging.properties File

Property | Purpose | Example
--- | --- | ---
log4j.appender.emlogAppender. MaxFileSize | When the Management Service log file reaches this size, the Management Service copies the logging data to a new rollover file and creates a new `emoms.log` log file. | log4j.appender.emlogAppender. MaxFileSize=20000000
log4j.appender.emlogAppender. MaxBackupIndex | This optional property indicates how many times the Management Service will rollover the log file to a new file name before deleting logging data. Note: Because the log file does not contain as much data as the trace file, it is usually not necessary to create more than one rollover file. As a result, this entry is not included in the properties file by default. | log4j.appender.emlogAppender. MaxBackupIndex=1
log4j.appender.emtrcAppender. MaxFileSize | When the Management Service trace file reaches this size, the Management Service copies the logging data to a new rollover file and creates a new `emoms.trc` log file. | log4j.appender.emtrcAppender. MaxFileSize=5000000
log4j.appender.emtrcAppender. MaxBackupIndex | This property indicates how many times the Management Services will rollover the trace file to a new file name before deleting tracing data. | log4j.appender.emtrcAppender. MaxBackupIndex=10

### 7.2.4 Controlling the Contents of the Management Service Trace File

By default, the Management Service will save all critical and warning messages to the `emoms.trc` file. However, you can adjust the amount of logging information that the Management Service generates.

To change the amount of logging information generated by the Management Service:

1. Stop the Management Service.

   See Also: "Controlling the Oracle Management Service"

2. Locate the `emomslogging.properties` file in the following directory:

       AS_HOME/sysman/config

3. Open the `emomslogging.properties` file with a text editor and locate the following entry:

       log4j.rootCategory=WARN, emlogAppender, emtrcAppender

4. Modify the value of the `log4j.rootCategory` parameter to one of the values shown in Table 7-2.

   Note: The values described in Table 7-2 are case-sensitive.

5. Restart the Management Service.

### 7.2.5 Controlling the Oracle Application Server Log Files

The Management Service is a J2EE application running in an Oracle Application Server Containers for J2EE (OC4J) instance within the Application Server. Different components of the Application Server generate their own log files. These files contain important information that can be used later by support personnel to troubleshoot problems.

Table 7-5 lists the location of the log files for some components.

Table 7-5 Component Log File Location

Component | Location
--- | ---
HTTP Server | ORACLE_HOME/Apache/Apache/logs/error_log.timeORACLE_HOME/Apache/Apache/logs/access_log.time
OC4J | ORACLE_HOME/j2ee/instance_name/logORACLE_HOME/j2ee/instance_name/application-deployments/application_name/application.log
OPMN | ORACLE_HOME/opmn/logs
Web Cache | ORACLE_HOME/webcache/logs

Refer to the Oracle Application Server Administrator's Guide for instructions on controlling the size and rotation of these log files.